Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

• WordPress.com Simple releases happen as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly:
  • Scheduled release: December 2, 2025

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

Thanks @westonruter, this looks great. I'd like to push a change to simplify the script, it doesn't seem like there's a reason to use an output buffer and wrap in <script> only to remove it later. I'll push a change for that and verify that it's still working correctly.

I'll update this comment as I perform testing.

Before (linked):

	<script data-ampdevmode type="text/javascript">
/* <![CDATA[ */
	var wpNotesIsJetpackClient = true;
	var wpNotesIsJetpackClientV2 = true;
		/* ]]> */
</script>

Before (unlinked):

	<script data-ampdevmode type="text/javascript">
/* <![CDATA[ */
	var wpNotesIsJetpackClient = true;
	var wpNotesIsJetpackClientV2 = true;
			var wpNotesLinkAccountsURL = 'https://example.com/wp-admin/admin.php?page=jetpack';
/* ]]> */
</script>

2e3d5a2

After (linked):

	<script data-ampdevmode>
		
		var wpNotesIsJetpackClient = true;
		var wpNotesIsJetpackClientV2 = true;
				
		
</script>

After (unlinked):

	<script data-ampdevmode>
		
		var wpNotesIsJetpackClient = true;
		var wpNotesIsJetpackClientV2 = true;
					var wpNotesLinkAccountsURL = "https://example.com/wp-admin/admin.php?page=jetpack";
				
		
</script>

With no output buffer

Linked:

	<script data-ampdevmode>
var wpNotesIsJetpackClient = true;
var wpNotesIsJetpackClientV2 = true;
</script>

Unlinked:

	<script data-ampdevmode>
var wpNotesIsJetpackClient = true;
var wpNotesIsJetpackClientV2 = true;
var wpNotesLinkAccountsURL = "https://example.com/wp-admin/admin.php?page=jetpack";
</script>

I've also followed these steps and the notifications bell works. A nonce attribute is added to the relevant script tag: <script data-ampdevmode nonce="{{Nonce value}}">

Install the Strict CSP plugin.
Ensure the admin bar Notes 🔔 dropdown works on the frontend.

Thanks @westonruter, this looks great. I'd like to push a change to simplify the script, it doesn't seem like there's a reason to use an output buffer and wrap in <script> only to remove it later. I'll push a change for that and verify that it's still working correctly.

@sirreal Thanks. Not a big deal, but the reason for this is is to have syntax highlighting in the IDE. This is previously discussed in Core-58664 with a follow-up in Core-59444. It's the reason for why wp_remove_surrounding_empty_script_tags() was introduced in core. What I see with my patch in PhpStorm:

Versus the latest changes:

Granted, the nowdoc you're using achieves much of the same effect at least in the first part of the JS, which is also discussed in Core-59444, albeit with the annoying thing you can't indent the final delimiter until we can bump PHP to 7.3.

Anyway, I don't feel strongly about this. It's a trivial amount of JS in any case, so the syntax highlighting is not really needed anyway.

Thanks for following up!